Method and apparatus for loading web page

ABSTRACT

The present disclosure relates to a pre-5 th -Generation (5G) or 5G communication system to be provided for supporting higher data rates Beyond 4 th -Generation (4G) communication system such as Long Term Evolution (LTE). 
     A method for receiving objects of a web page by a terminal is provided. The method includes determining sizes of the objects, determining a number of Transmission Control Protocol (TCP) connections to be allocated for each of a plurality of domains connected to the web page, based on estimated sizes of the objects, determining a reception order of the objects to be received in the domains for each domain based on a size of a Congestion Window (CWND) of a server, and receiving the objects in the determined reception order.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit under 35 U.S.C. §119(e) of a U.S.Provisional application filed on May 15, 2014 in the U.S. Patent andTrademark Office and assigned Ser. No. 61/993,684, the entire disclosureof which is hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to a method and apparatus for efficientlyloading a web page.

BACKGROUND

To meet the demand for wireless data traffic having increased sincedeployment of 4^(th)-Generation (4G) communication systems, efforts havebeen made to develop an improved 5^(th)-Generation (5G) or pre-5Gcommunication system. Therefore, the 5G or pre-5G communication systemis also called a ‘Beyond 4G Network’ or a ‘Post Long-Term Evolution(LTE) System’.

The 5G communication system is considered to be implemented in higherfrequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higherdata rates. To decrease propagation loss of the radio waves and increasethe transmission distance, the beamforming, massive multiple-inputmultiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna,an analog beam forming, large scale antenna techniques are discussed in5G communication systems.

In addition, in 5G communication systems, development for system networkimprovement is under way based on advanced small cells, cloud RadioAccess Networks (RANs), ultra-dense networks, device-to-device (D2D)communication, wireless backhaul, moving network, cooperativecommunication, Coordinated Multi-Points (CoMP), reception-endinterference cancellation and the like.

In the 5G system, Hybrid FSK and QAM Modulation (FQAM) and slidingwindow superposition coding (SWSC) as an advanced coding modulation(ACM), and filter bank multi carrier (FBMC), non-orthogonal multipleaccess (NOMA), and sparse code multiple access (SCMA) as an advancedaccess technology have been developed.

A time required for loading a web page in a web browser or webapplications depends on some factors such as a design of the web page,an algorithm of the web browser, a Round Trip Time (RTT) between a userand a server, network parameters like a communication bandwidth, and soforth.

Generally, on a web page, there are various objects such as a Hyper TextMarkup Language (HTML) page, a Cascaded Style Sheet (CS S), aJavaScript, an image, and the like. A network consumes a significantamount of time to receive all embedded objects for a web page to bedisplayed.

Web objects of the related art are received according to a referenceorder of corresponding objects in a main HTML page. Some of objectsreferred to through JavaScript are received after execution ofJavaScript. Since web objects are received over a Transmission ControlProtocol (TCP) connection, the effective network throughput isunderutilized.

Due to a slow start phase of a TCP mechanism, web developers usemultiple domains to open up many parallel TCP connections between aterminal and a server. This method is called domain sharding. In domainsharding, a web browser of the terminal may check only a domain name,and a plurality of domain names may be in a physical server having oneIP address.

For reference, a web browser has a limitation on a number of parallelTCP connections, and typically, the number of parallel TCP connectionsallowed for the web browser is limited to 6. Meanwhile, to receivemultiple objects on several domains having the limited TCP connections,reception optimization is needed to minimize a Page Loading Time (PLT)by efficiently performing reception.

The above information is presented as background information only toassist with an understanding of the present disclosure. No determinationhas been made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the present disclosure.

SUMMARY

Aspects of the present disclosure are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentdisclosure is to provide a method and apparatus for reducing a PageLoading Time (PLT).

Another aspect of the present disclosure is to provide a method andapparatus for determining a number of Transmission Control Protocol(TCP) connections to be allocated for each domain to receive objectsincluded in a web page.

Another aspect of the present disclosure is to provide a method andapparatus for determining a reception order of objects included in a webpage.

In accordance with an aspect of the present disclosure, a method forreceiving objects of a web page by a terminal is provided. The methodincludes determining sizes of the objects, determining a number of TCPconnections to be allocated for each of a plurality of domains connectedto the web page, based on estimated sizes of the objects, determining areception order of the objects to be received in the domains for eachdomain based on a size of a Congestion Window (CWND) of a server, andreceiving the objects in the determined reception order.

In accordance with another aspect of the present disclosure, a terminalapparatus for receiving objects of a web page is provided. The terminalapparatus includes a controller configured to determine sizes of theobjects, to determine a number of TCP connections to be allocated foreach of a plurality of domains connected to the web page, based onestimated sizes of the objects, to determine a reception order of theobjects to be received in the domains for each domain based on a size ofa CWND of a server, and to receive the objects in the determinedreception order and a browser configured to receive the objects in thedetermined reception order.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the present disclosure will be more apparent from thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a block diagram illustrating a structure of a terminalaccording to an embodiment of the present disclosure;

FIG. 2 is a flowchart illustrating a method for loading a web pageaccording to an embodiment of the present disclosure;

FIG. 3 is a flowchart illustrating a process of determining a number ofTransmission Control Protocol (TCP) connections per domain according toan embodiment of the present disclosure;

FIG. 4 is a flowchart illustrating a process of scheduling objectsaccording to an embodiment of the present disclosure;

FIG. 5 illustrates an example in which objects are scheduled overrespective TCP connections for each domain according to an embodiment ofthe present disclosure; and

FIG. 6 illustrates an example in which scheduling is performed by aHyper Text Transfer Protocol (HTTP) range request without an object sizeestimation of a terminal according to an embodiment of the presentdisclosure.

Throughout the drawings, like reference numerals will be understood torefer to like parts, components, and structures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the present disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thepresent disclosure. In addition, description of well-known functionsconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of the presentdisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of the presentdisclosure is provided for illustration purpose only and not for thepurpose of limiting the present disclosure as defined by the appendedclaims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

Although the terms such as “first” and “second” used in the variousembodiments of the present disclosure may modify various elements of thevarious embodiments, these terms do not limit the correspondingelements. For example, these terms do not limit an order and/orimportance of the corresponding elements. These terms may be used forthe purpose of distinguishing one element from another element. Forexample, a first user device and a second user device all indicate userdevices or may indicate different user devices. For example, a firstelement may be named as a second element without departing from theright scope of the various embodiments of the present disclosure, andsimilarly, a second element may be named as a first element. The term“and/or” includes a combination of a plurality of related provided itemsor any one of the plurality of related provided items.

An apparatus and method proposed in the present disclosure may beapplied to various communication systems such as a Long-Term Evolution(LTE) mobile communication system, an LTE-Advanced (LTE-A) mobilecommunication system, a High Speed Downlink Packet Access (HSDPA) mobilecommunication system, a High Speed Uplink Packet Access (HSUPA) mobilecommunication system, a High Rate Packet Data (HRPD) mobilecommunication system of the 3^(rd) Generation Project Partnership 2(3GPP2), a Wideband Code Division Multiple Access (WCDMA) mobilecommunication system of the 3GPP2, a CDMA mobile communication system ofthe 3GPP2, the Institute of Electrical and Electronics Engineers (IEEE)802.16m communication system, an Evolved Packet System (EPS), a MobileInternet Protocol (Mobile IP) system, and so forth.

Before various embodiments of the present disclosure are described, themain concept of the present disclosure will be described in brief.

The basic concept of a web page loading scheme proposed in the presentdisclosure is determining a reception order of objects based on a sizeof a Congestion Window (CWND) of a sender and sizes of objects to bereceived. For reference, herein, an operation of determining a receptionorder of objects may be referred to as “scheduling.”

The web page loading scheme proposed in the present disclosure may beapplied to a web browser and a web application of a user terminal(hereinafter, simply referred to as a “terminal”) such as a PersonalComputer (PC), a tablet PC, a smart phone, or the like.

FIGS. 1 through 6, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way that would limit the scope of the disclosure. Those skilled inthe art will understand that the principles of the present disclosuremay be implemented in any suitably arranged communications system. Theterms used to describe various embodiments are exemplary. It should beunderstood that these are provided to merely aid the understanding ofthe description, and that their use and definitions in no way limit thescope of the present disclosure. Terms first, second, and the like areused to differentiate between objects having the same terminology andare in no way intended to represent a chronological order, unless whereexplicitly stated otherwise. A set is defined as a non-empty setincluding at least one element.

FIG. 1 is a block diagram illustrating a structure of a terminalaccording to an embodiment of the present disclosure.

Referring to FIG. 1, a terminal 100 is illustrated, where the terminal100 may include a browser/application 110 (hereinafter, simply referredto as a “browser”) and a transceiver 120. The transceiver 120 performsdata transmission and reception with a server (not shown). Thebrowser/application 110 may include a browser engine 111 and acontroller 113. The controller 113 receives objects of a web pagereceived through the transceiver 120 and performs reception optimizationfor the objects to deliver the objects to the browser engine 111,according to a method proposed in the present disclosure. The browserengine 111 receives the objects and loads the web page.

FIG. 2 is a flowchart illustrating a method for loading a web pageaccording to an embodiment of the present disclosure.

Referring to FIG. 2, a flowchart is illustrated, such that in operation201, a terminal identifies a plurality of objects included in a web pageby analyzing information associated with the web page. The informationassociated with the web page refers to information describing aconfiguration of the web page, and may be, for example, a Hyper TextMarkup Language (HTML) file and/or Cascaded Style Sheet (CSS) files. Forreference, a CSS file is a style sheet which previously stores thereinan overall style of a web document, and the CSS file may maintainoverall consistency of the web page when compared to an HTML, and reducea need to designate a detailed style used in the web page.

Upon receiving JavaScripts included in the web page, the terminal mayscan a Java code or run JavaScript in advance to identify embeddedobjects.

Once the objects are identified, the terminal classifies the objectsinto critical (or important) resources and non-critical (unimportant)resources according to a general web page design principle. An exampleof a critical resource may be an Index.html file, a CSS, or a JavaScriptincluded in an HTML header. An example of a non-critical resource may bea JavaScript defined in an HTML ending part, images, or a flash.

In another embodiment where information about critical/non-criticalresources is classified, the server may indicate “critical/non-critical”by using special tags in the HTML page/header.

The reason for classification according to criticality (or importance)of objects is that a delay of a critical resource that may affect aninitial rendering time of the web page is not preferable because theobjects are to be received based on their sizes in the presentdisclosure, such that critical objects need to be receivedpreferentially.

In operation 203, the terminal determines sizes of the objectsidentified in operation 201.

Object size determination may be performed by statistically estimatingthe object sizes based on types of the objects or by using sizeinformation of the objects, included in the information associated withthe web page or a separate signaling message. A detailed example isprovided below.

In an embodiment of the present disclosure, an HTML page provides onlyobjects and types of the objects, such that a file size of an object maydiffer from object to object. Thus, to determine a size of an object fordifferent file types of objects, various methods may be used. Forexample, for an HTML, a CSS, and a JavaScript, an object size may bestatistically estimated. For an image object, the size of the object maybe estimated based on an image type and an image resolution. Statisticestimation of predetermined size and type may be performed in a terminal

In another embodiment, the size of an object may be embedded in an HTMLpage.

In another embodiment, the size of an object may be provided to theterminal by the server through explicit messages.

In operation 205, the terminal determines a number of TransmissionControl Protocol (TCP) connections for each domain (or domain-specificTCP connections) based on the sizes of objects to be received in eachdomain. A detailed process of operation 205 will be descried withreference to FIG. 3.

FIG. 3 is a flowchart illustrating a process of determining a number ofdomain-specific TCP connections according to an embodiment of thepresent disclosure.

Referring to FIG. 3, a flowchart is illustrated, such that in operation301, a terminal statistically estimates an average reception time forobjects having different sizes based on a Maximum Segment Size (MSS)unit per domain. The MSS means a maximum size of a segment permitted inreception of an object, and a time for receiving the object may bedetermined by the number of MSSs necessary for reception of the object.

In operation 303, the terminal calculates a time for receiving eachobject (or a reception time for each object) with respect to differentnumbers of TCP connections for each domain.

In operation 305, the terminal determines a minimum reception time T_(N)in each domain. Herein, N indicates an index of a domain.

In operation 307, the terminal selects a maximum value (T_(MAX) of adomain K) from among domain-specific minimum reception times determinedin operation 305.

In operation 309, the terminal determines the number of TCP connectionsfor other domains, such that a reception time for each of the otherdomains may not exceed the maximum value T_(MAX).

The foregoing process will be described using an example. It is assumedthat a web page includes 10 objects O1, O2, . . . , O10 having differentsizes; <O1, O2, O3> out of the 10 objects are received in a first domainD1 among four domains D1, D2, D3, and D4; <O4, O5> are received in asecond domain D2; <O6, O7, O8> are received in a third domain D3; and<O9, O10> are received in a fourth domain D4.

Under the above assumption, the method illustrated in FIG. 3 will bedescribed.

In operation 301, an average reception time for objects to be receivedin the domains D1, D2, D3, and D4 is estimated.

In operation 303, a reception time for each of the objects O1, O2, andO3 received in the domain D1 is estimated when the domain D1 has one TCPconnection. In addition, a reception time for each of the objects O1,O2, and O3 is calculated when the domain D1 has two TCP connections. Inthe same manner, a reception time for each of the objects O1, O2, and O3is calculated in each of cases where the domain D1 has three through sixTCP connections. This process is equally applied to the domains D2, D3,and D4, to calculate a reception time for each object to be received ineach domain.

In operation 305, the terminal calculates a domain-specific minimumreception time based on an object-specific reception time calculated inoperation 303. As a result, it is assumed that a minimum reception timeT₁ in the domain D1 is determined to be 400 ms, a minimum reception timeT₂ in the domain D2 is determined to be 200 ms, a minimum reception timeT₃ in the domain D3 is determined to be 800 ms, and a minimum receptiontime T₄ in the domain D4 is determined to be 350 ms.

In operation 307, the terminal determines a maximum value among T₁through T₄ as T_(MAX). In this example, T_(MAX)=T₃=800 ms.

In operation 309, the terminal determines the number of TCP connectionsin the domains D1, D2, and D4, such that the reception times in thedomains D1, D2, and D4 do not exceed T_(MAX)=T₃=800 ms. For reference,the number of TCP connections in the domain D3 is set to the number ofTCP connections corresponding to T₃=800 ms. When determining the numberof domain-specific TCP connections, the terminal may equally distributeobjects to TCP connections of each domain based on sizes of objectsreceived in each domain.

Referring back to FIG. 2, in operation 207, each object is scheduled foreach domain having the number of TCP connections determined in operation205. In the present disclosure, reception of each object is scheduledbased on a size of a CWND in a TCP sender, that is, a server. Forreference, the size of the CWND is determined in the server and may notbe determined in the terminal. However, the server may adjust the sizeof the CWND in response to a response signal (Acknowledgement(ACK)/Negative ACK (HACK)) from the terminal. Thus, the terminal mayestimate the size of the CWND determined by the server based on theresponse signal the terminal has transmitted to the server.

Meanwhile, an importance of objects to be received may be determinedbased on a data size in the manner described in the previous operation.In an embodiment of the present disclosure, importance of the objects isdetermined based on the sizes of the objects and an object having highimportance is preferentially received. In addition, objects requiringthe same time to be received in a domain may be grouped. The timerequired for receiving the objects may be determined based on the numberof MSSs. A list of the objects may be updated each time the objects areidentified in operation 201.

FIG. 4 is a flowchart illustrating a process of scheduling objectsaccording to an embodiment of the present disclosure.

Referring to FIG. 4, a flowchart is illustrated, wherein a scheme forscheduling objects according to the present disclosure selects oneobject from a list of object groups, taking a CWND size of a TCPconnection into account when the arbitrary TCP connection is availableamong TCP connections being set in one domain. That is, for an availableidle-state TCP connection, a CWND size of the TCP connection isestimated, an object is selected based on the estimated CWND size, andthe selected object is scheduled over the TCP connection, as will bedescribed in detail below.

Referring to FIG. 4, in operation 401, a terminal determines whether allobjects are scheduled; if all objects are scheduled, the terminalterminates the operation. On the other hand, if at least one object hasnot been scheduled, the terminal proceeds to operation 403.

In operation 403, the terminal determines whether the idle-state TCPconnection is available. If, in operation 403, the terminal determinesthat the TCP connection is not available, the process returns tooperation 401. However, if, in operation 403, the terminal determinesthat the TCP connection is available, then the terminal proceeds tooperation 405 to obtain the estimated CWND size corresponding to theidle-state TCP connection.

Next, in operation 407, the terminal selects an object based on theestimated CWND size. Object selection based on the CWND size will bedescribed later.

In operation 409, the terminal schedules the selected object in the TCPconnection. After operation 409 the process returns to operation 401.

A scheme for selecting the object based on the CWND size in operation407 of FIG. 4 will be described below.

As mentioned above, in an embodiment of the present disclosure, for agiven TCP, an object is selected based on a currently estimated CWNDsize. First, an object is selected from a group having a CWND estimatedto have the same size. Thereafter, an object is selected from a grouphaving a smaller-size CWND to preferentially receive objects havingsmall sizes. Objects are determined from the group (a current CWND+anext CWND) to schedule objects that may be received during 2 Round TripTimes (RTTs). Objects are then scheduled from a group having the nexthigher CWND.

FIG. 5 illustrates an example in which objects are scheduled overrespective TCP connections for each domain according to an embodiment ofthe present disclosure.

Referring to FIG. 5, an illustration is provided, wherein critical andnon-critical embedded objects are included in a browser/application andwherein four domains D1 501, D2 502, D3 503, and D4 504, six TCPconnections 511 through 516 are set in the domain D1 501, four TCPconnections 521 through 524 are set in the domain D2 502, two TCPconnections 531 and 532 are set in the domain D3 503, and five TCPconnections 541 through 545 are set in the domain D4 504. That is, TCPconnections are set for each domain based on the number of TCPconnections determined for each domain according to the above-describedembodiment of the present disclosure.

Referring to FIG. 5, objects to be received over respective TCPconnections are scheduled. For example, in a TCP connection 1 511 of thedomain D1 501, three objects O1, O7, and O13 are scheduled. In other TCPconnections, objects are also scheduled. This example uses objectscheduling per domain as described above. FIG. 5 illustrates howadditional objects are scheduled for different connections of thedifferent domains 501, 502, 503 and 504.

In the foregoing description, objects have been scheduled, taking anestimated CWND size into account. In another embodiment, objects mayalso be scheduled without estimation of a CWND size. For example, basedon sizes of objects, the objects may be scheduled in an increasing orderof size. That is, since the sizes of the objects have already beendetermined, the objects may be sorted in an ascending order of objectsize and the objects sorted in the ascending order may be scheduled whena TCP connection is available.

Meanwhile, the performance of scheduling based on CWND size estimationmainly depends on object size estimation. In another embodiment of thepresent disclosure, the terminal performs scheduling by using a HyperText Transfer Protocol (HTTP) range request, without object sizeestimation.

The HTTP range request may be used to receive an object corresponding toa part specifying the amount of data desired by the terminal. If theHTTP range request is used separately from a partial file, informationabout an object size may be obtained through a response thereto.

First, each object is partially received based on the current CWND size.In this process, if an actual object size is smaller than a rangerequested by the HTTP range request from the terminal, some of objectsmay have been received. The remaining files may be received using theabove-described scheduling algorithm according to the presentdisclosure.

FIG. 6 illustrates an example in which scheduling is performed by anHTTP range request without an object size estimation of a terminalaccording to an embodiment of the present disclosure.

Referring to 6, an illustration is provided, wherein in scheduling usingan HTTP range request, each object is divided into two parts. That is, atotal of eighteen objects are assumed to be scheduled over six TCPconnections 601 through 606. Each of the eighteen objects is dividedinto two parts. For example, it can be seen that object O1 is dividedinto parts O1-1 and O1-2, object O2 is divided into parts O2-1 and O2-2,object O3 is divided into parts O3-1 and O3-2, object O4 is divided intoparts O4-1 and O4-2, object O5 is divided into parts O5-1 and O5-2,object O6 is divided into parts O6-1 and O6-2, object O7 is divided intoparts O7-1 and O7-2, object O8 only has one part O8-1, object O9 isdivided into parts O9-1 and O9-2, object O10 is divided into parts O10-1and O10-2, object O11 is divided into parts O11-1 and O11-2, object O12is divided into parts O12-1 and O12-2, object O13 only has one partO13-1, object O14 only has one part O14-1, object O15 is divided intoparts O15-1 and O15-2, object O16 only has one part O16-1, object O17 isdivided into parts O17-1 and O17-2, and the object O18 only has one partO18-1. The sizes of the first parts O1-1 through O18-1 divided from therespective objects O1 through O18 are the same as the currentlyestimated CWND size.

Once each object is divided into two parts in this way and the firstparts O1-1 through O18-1 of the respective objects O1 through O18 arereceived, the second parts (e.g., O1-2) of the respective objects arescheduled and received using the above-described scheduling according tothe present disclosure.

So far, the various embodiments of the present disclosure have beendescribed.

According to the various embodiments of the present disclosure, a timefor receiving objects may be optimized and the number of TCP connectionsmay be reduced according to the optimized reception time, therebyefficiently using resources. Moreover, the amount of computation, amemory capacity, and power consumption in the terminal may be reduced.

The foregoing embodiments of the present disclosure may be applied toany web browser and a web application that receive web objects throughthe HTTP. The mechanism may improve a page loading time when many webobjects exist. The HTTP range request mechanism does not need any filesize estimation, facilitating implementation.

Particular aspects of the present disclosure may also be implemented asa computer readable code in a computer readable recording medium. Thecomputer readable recording medium may be any type of data storagedevice that may store data readable by a computer system. Examples ofrecord-mediums readable by the computer may include a Read-Only Memory(ROM), a Random-Access Memory (RAM), a Compact Disc-ROM (CD-ROM),magnetic tapes, floppy disks, optical data storage devices, carrierwaves (such as data transmission through the Internet). Further,functional programs, codes and code segments for achieving the presentdisclosure may be easily interpreted by programmers skilled in the artwhich the present disclosure pertains to.

Therefore, the present disclosure includes a program including codes forimplementing an apparatus or method claimed in an arbitrary claim and amachine (computer)-readable storage medium for storing such a program.The program may be electronically transferred through an arbitrarymedium such as a communication signal delivered through a wired orwireless connection, and the present disclosure properly includesequivalents thereof

The apparatus according to an embodiment of the present disclosure mayreceive and store the program from a program providing device connectedin a wired or wireless manner. The program providing device may includea memory for storing a program including instructions for instructingthe apparatus to execute a preset method, information necessary for themethod, a communication unit for performing wired or wirelesscommunication with the apparatus, and a controller for transmitting acorresponding program to the apparatus at the request of the apparatusor automatically.

While the present disclosure has been shown and described with referenceto various embodiments thereof, it will be understood by those skilledin the art that various change in form and details may be made thereinwithout departing from the spirit and scope of the present disclosure asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A method for receiving objects of a web page by aterminal, the method comprising: determining sizes of the objects;determining a number of Transmission Control Protocol (TCP) connectionsto be allocated for each of a plurality of domains connected to the webpage, based on estimated sizes of the objects; determining a receptionorder of the objects to be received in the domains for each domain basedon a size of a Congestion Window (CWND) of a server; and receiving theobjects in the determined reception order.
 2. The method of claim 1,wherein the determining of the sizes of the objects comprises:determining the sizes of the objects by one of statistically estimatingthe sizes of the objects based on types of the objects, using sizeinformation regarding the objects, included in information associatedwith the web page, and using size information regarding the objects,included in a separate message received from a server.
 3. The method ofclaim 1, wherein the determining of the number of TCP connectionscomprises: determining an average reception time per domain based on thesizes of the objects; calculating reception times for all of the objectswith respect to different numbers of TCP connections for each domain;determining minimum reception times (T_(N)) for the respective domains;determining a maximum value (T_(MAX)) from among the minimum receptiontimes per domain; and determining the number of TCP connections for thedomains other than a domain having the maximum value (T_(MAX)), suchthat the reception times for the other domains do not exceed the maximumvalue (T_(MAX)).
 4. The method of claim 1, further comprising:determining an importance of the objects; and preferentially receivingobjects having high importance according to the determined importance.5. The method of claim 1, wherein the determining of the reception orderof the objects comprises: estimating a size of a CWND of a TCPconnection available in a domain; and selecting an object based on theestimated size of the CWND.
 6. A terminal apparatus for receivingobjects of a web page, the terminal apparatus comprising: a controllerconfigured to: determine sizes of the objects, determine a number ofTransmission Control Protocol (TCP) connections to be allocated for eachof a plurality of domains connected to the web page, based on estimatedsizes of the objects, determine a reception order of the objects to bereceived in the domains for each domain based on a size of a CongestionWindow (CWND) of a server, and receive the objects in the determinedreception order; and a browser configured to receive the objects in thedetermined reception order.
 7. The terminal apparatus of claim 6,wherein the controller is further configured to determine the sizes ofthe objects by one of statistically estimating the sizes of the objectsbased on types of the objects, using size information regarding theobjects, included in information associated with the web page, and usingsize information regarding the objects, included in a separate messagereceived from a server.
 8. The terminal apparatus of claim 6, wherein,to determine the number of TCP connections, the controller is furtherconfigured to: determine an average reception time per domain based onthe sizes of the objects; calculate reception times for all of theobjects with respect to different numbers of TCP connections for eachdomain; determine minimum reception times (T_(N)) for the respectivedomains; determine a maximum value (T_(MAX)) from among the minimumreception times per domain; and determine the number of TCP connectionsfor the domains other than a domain having the maximum value (T_(MAX))such that the reception times for the other domains do not exceed themaximum value (T_(MAX)).
 9. The terminal apparatus of claim 6, whereinthe controller is further configured to determine an importance of theobjects and preferentially receives objects having high importanceaccording to the determined importance.
 10. The terminal apparatus ofclaim 6, wherein, to determine the reception order of the objects, thecontroller is further configured to: estimate a size of a CWND of a TCPconnection available in a domain; and select an object based on theestimated size of the CWND.
 11. The terminal apparatus of claim 6,wherein the controller is further configured to determine whether all ofthe objects are scheduled; and wherein, if all of the objects are notscheduled, the controller is further configured to: determine whether anidle-state TCP connection is available, and if the idle-state TCPconnection is available the controller is further configured to obtainan estimated CWND size corresponding to the idle-state TCP connection.